home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Developer Toolbox 6.1
/
SGI Developer Toolbox 6.1 - Disc 1.iso
/
toolbox
/
documents
/
irix6.2
/
TIP
/
TIPtoc.txt
< prev
Wrap
Text File
|
1996-11-11
|
11KB
|
251 lines
Back to IRIX 6.2 | Download | HTML
-------------------------
Topics in IRIX Programming
Document Number 007-2478-003
Table Of Contents
This guide contains the following chapters/sections.
ALL FILE INCLUDED HERE ARE COMPRESSED PostScript FILES
-------------------------------------------------------------
* Title Page (2 pages)
* Table of Contents (12 pages)
* List of Examples (2 pages)
* List of Figures (2 pages)
* List of Tables (2 pages)
* About This Manual, (4 pages)
Chapter 1 header (2 pages)
1. Chapter 1 "Process Address Space," (28 pages)
When planning a complex program, you must understand how IRIX
creates the virtual address space of a process, and how you can
modify the normal behavior of the address space. The major topics
covered here are:
+ "Defining the Address Space"
tells what the address space is and how it is created.
+ " Interrogating the Memory System"
summarizes the ways your program can get information about
the address space.
+ " Mapping Segments of Memory"
documents the different ways that you can create new memory
segments with predefined contents.
+ " Locking Pages in Memory"
discusses when and how to lock pages of virtual memory to
avoid page faults.
+ " Additional Memory Features"
summarizes functions for address space management.
Chapter 2 header, (2 pages)
2. Chapter 2, "Interprocess Communication," (88 pages)
The term interprocess communication (IPC) describes any method of
sending data from one running process to another. IPC is commonly
used to allow processes to coordinate the use of shared data
objects, for instance, to let two programs update the same data in
memory without interfering with each other, or to make data
acquired by one process available to others. IRIX supports a wide
variety of IPC mechanisms.
This chapter describes IPC and covers the following topics:
+ "Types of Interprocess Communication Available"
gives a brief overview of the types of IPC available.
+ "IRIX IPC"
explains IRIX shared arenas, locks, semaphores, and shared
memory.
+ "System V IPC"
describes System V messages, semaphores, and shared memory.
chapter 3 header, (2 pages)
3. Chapter 3, "Models of Parallel Computation," (22 pages)
Silicon Graphics, makes multiprocessor computer systems. You can
use any of several programming models to exploit the parallel
capabilities of the hardware. This chapter reviews the parallel
programming models, supplying enough information that you can
select one model. Pointers to more detailed documentation of each
model are included. The major topics are:
+ "Parallel Hardware and Programming Models"
provides a quick survey of the programming models and their
relationship to the hardware.
+ "Using Statement-Level Parallelism"
discusses using fine-grained parallel execution in Fortran
and C.
+ "Using Process-Level Parallelism"
provides an overview of the use of coordinated UNIX processes
for parallel execution.
+ "Using MPI and PVM"
compares these two interfaces.
chapter 4 header, (2 pages)
4. Chapter 4, "File and Record Locking," (18 pages)
This chapter describes how you can use file and record locking
capabilities. Examples are given for the correct use of record
locking. Misconceptions about the amount of protection that record
locking affords are dispelled. Record locking should be viewed as
a synchronization mechanism, not a security mechanism.
The chapter includes these topics
+ "Overview of File and Record Locking"
presents an introduction to locking mechanisms.
+ "Terminology"
defines some common terms about locking.
+ "Using Record Locking"
covers using access permissions, locking files, and getting
lock information.
+ "Selecting Advisory or Mandatory Locking"
describes mandatory locking and record locking across
systems.
chapter 5 header, (2 pages)
5. Chapter 5, "Working With Fonts," (22 pages)
This chapter describes how to work with fonts on Silicon Graphics
computers. It begins with an introduction to fonts and digital
typography. Then it explains which fonts are available and how to
install additional fonts. It also covers how to download outline
fonts in the Type 1 format to a PostScript printer.
This chapter contains these sections:
+ "Font Basics"
defines fonts and provides some general background
information.
+ "Using Fonts With the X Window System"
discusses some of the most useful font utilities of the X
Window SystemΣ.
+ "Installing and Adding Font and Font Metric Files"
explains how to install and add font files and font metric
files for system-wide use.
+ "Downloading a Type 1 Font to a PostScript Printer"
explains how to download a Type 1 font to a PostScript
printer.
chapter 6 header, (2 pages)
6. Chapter 6, "Internationalizing Your Application," (82 pages)
Internationalization is the process of generalizing an application
so that it can easily be customized -- or localized -- to run in
more than one language environment. You can provide
internationalized software that will produce output in a user's
native language, format data (such as currency values and dates)
according to local standards, and tailor software to a specific
culture.
This chapter describes how to create such an application. It
contains the following major sections:
+ "Overview"
presents an introduction to internationalization and defines
some common terms.
+ "Additional Reading on Internationalization"
explains how to set the current locale and limitations of the
locale system.
+ "Character Sets, Codesets, and Encodings"
describes various ways of encoding characters,
+ "Cultural Items"
discusses the ways in which different cultures affect the way
a string can be viewed, for example in outputting or
collating.
+ "Locale-Specific Behavior"
covers native language support (NLS) and the NLS database,
regular expressions, and cultural data.
+ "Strings and Message Catalogs"
describes how to create and use catalogs of messages to send
diagnostic information to users in various locales.
+ "Internationalization Support in X11R6"
describes internationalization support provided by X11,
Release 6 (including features from X11R5).
+ "Internationalization Support in Motif"
points to information describing how to internationalize a
Motif application.
+ "User Input"
discusses the translation of keyboard events into
programmatic character strings for a variety of keyboards.
+ "GUI Concerns"
discusses internationalizing applications that use graphical
user interfaces (GUIs)
+ "Popular Encodings"
presents some common non-ASCII encodings.
For a list of ISO 3166 country names and abbreviations, see
Appendix A, "ISO 3166 Country Names and Abbreviations." You can
find detailed information about fonts in Chapter 5, "Working With
Fonts." Also, you can find additional information about
internationalizing an application in the Indigo Magic Desktop
Integration Guide.
appendix A header, (2 pages)
* Appendix A, "ISO 3166 Country Names and Abbreviations," (4 pages)
Table A-1 lists the ISO 3166 country codes, alphabetized by
country name (the table reads from left to right, and top to
bottom).
appendix B header, (2 pages)
* Appendix B, "Converting PVM Applications to MPI," (24 pages)
PVM and MPI are two popular message-passing libraries that are in
use across a variety of platform. MPI assimilates the most
attractive features of a number of existing message-passing
systems, including PVMs (see "Choosing Between MPI and PVM").
Silicon Graphics has adopted MPI as the message-passing model for
the POWER CHALLENGEarray and other Array products, and provides a
low-latency, high-bandwidth implementation of MPI for these
systems. Programmers are encouraged to write new message-passing
applications using MPI, and to port existing applications to MPI
when that is feasible.
Many existing message-passing applications use the PVM library,
owing to its widespread use for the last five years. In order to
support this application base, Silicon Graphics, Inc. also
supports PVM for Array systems. However, the design of the MPI
interface is such that the performance of the MPI implementation
on these systems will always be better than the performance of
PVM. To obtain best performance, porting parallel programs from
PVM to MPI is recommended.
This appendix covers the following main topics:
+ "Differences Between PVM and MPI"
gives an overview of the differences that are likely to cause
difficulty in porting.
+ "Comparing Library Routines"
lists the PVM routines and their MPI counterparts, when a
counterpart exists.
+ "Converting a PVM Program to an MPI Program"
covers the tasks involved in porting.
+ "Example Programs"
shows example conversions.
* Index, (12 pages)
* Tech Pubs Wants To Hear From You, (2 pages)
----------------------------------------------------------------------------
Select any combo of files you'd like to send yourself a compressed tar image
of. Executables/scripts are indicated with a trailing `*' character.
(Depending upon the browser, it may be necessary to hold down the Ctrl key
to select/deselect disjoint items.)
a compressed tar image of the above-selected items.
OR, ...
a compressed tar image of the entire TIP directory.
----------------------------------------------------------------------------
Copyright ⌐ 1996, Silicon Graphics, Inc.